Multicomputer Processing of an Event Request From an Event Origination Device With Centralized Event Orchestration

ABSTRACT

Aspects of the disclosure relate to multicomputer processing of an event request from an event origination device with centralized event orchestration. A computing platform may receive, from an event origination device, an event request for an event. Subsequently, the computing platform may determine a sub-event associated with the event. Next, the computing platform may receive, from an event dataset customization engine, an event customized dataset generated for the sub-event. Then, the computing platform may generate, based on the sub-event associated with the event received from the event origination device, one or more event orchestration commands directing a sub-event processing device to execute the sub-event. Thereafter, the computing platform may receive, from the sub-event processing device, a results dataset. Subsequently, the computing platform may update, based on the results dataset, a master event dataset associated with the event.

BACKGROUND

Aspects of the disclosure relate to electrical computers, digitalprocessing systems, and multicomputer data transferring. In particular,one or more aspects of the disclosure relate to multicomputer processingof an event request from an event origination device with centralizedevent orchestration.

As computer systems are increasingly utilized to provide automated andelectronic services, execution of these services may requireincreasingly complex coordination between the computer systems, andensuring timely and accurate coordination may be increasingly important.In many instances, however, it may be difficult to implement and executethe coordinated data flows for the services between the computingsystems while also optimizing the efficient and effective technicaloperations of the computer systems that provide such automated andelectronic services.

SUMMARY

Aspects of the disclosure provide effective, efficient, scalable, andconvenient technical solutions that address and overcome the technicalproblems associated with coordinating complex event data flows and eventdata management between computer systems, and optimizing the efficientand effective technical operations of computer systems. In particular,one or more aspects of the disclosure provide techniques for processingan event request from an event origination device using multicomputerprocessing and centralized event orchestration to improve datamanagement and enhance technical performance.

In accordance with one or more embodiments, a computing platform havingat least one processor, a memory, and a communication interface mayreceive, via the communication interface, from a first event originationdevice, a first event request for a first event. Then, the computingplatform may determine a first sub-event associated with the firstevent. Subsequently, the computing platform may receive, via thecommunication interface, from an event dataset customization engine, afirst customized dataset generated for the first sub-event. Thereafter,the computing platform may generate, based on the first sub-eventassociated with the first event received from the first eventorigination device, one or more first event orchestration commandsdirecting a first sub-event processing device to execute the firstsub-event. Subsequently, the computing platform may send, via thecommunication interface, to the first sub-event processing device, thefirst customized dataset and the one or more first event orchestrationcommands directing the first sub-event processing device to execute thefirst sub-event. Then, the computing platform may receive, via thecommunication interface, from the first sub-event processing device, afirst results dataset. Thereafter, the computing platform may update,based on the first results dataset, the first master event datasetassociated with the first event.

In some embodiments, determining the first sub-event may includedetermining a first event type of the first event, accessing, in anevent protocol database, a first event protocol of the first event type,and determining the first sub-event based on contents of the first eventprotocol. In some instances, the computing platform may, prior todetermining the first sub-event associated with the first event, send acommand to the event dataset customization engine to generate the firstmaster event dataset within the event dataset customization engine. Insome instances, the first customized dataset may be generated based inpart on the first master event dataset.

In some embodiments, the computing platform may validate contents of thefirst event request with input data requirements specified by the firstevent protocol.

In some embodiments, the computing platform may validate contents of thefirst results dataset with output data requirements specified for thefirst sub-event within the first event protocol.

In some embodiments, the computing platform may determine a secondsub-event associated with the first event. Then, the computing platformmay receive, via the communication interface and from an event datasetcustomization engine, a second customized dataset generated for thesecond sub-event. Thereafter, the computing platform may generate, basedon the second sub-event for the first event received from the firstevent origination device, one or more second event orchestrationcommands directing a second sub-event processing device to execute thesecond sub-event. Subsequently, the computing platform may send, via thecommunication interface and via an external event processing interface,to the second sub-event processing device, the second customized datasetand the one or more second event orchestration commands directing thesecond sub-event processing device to execute the second sub-event.Then, the computing platform may receive, via the communicationinterface and via the external event processing interface, from thesecond sub-event processing device, a second results dataset.Thereafter, the computing platform may update, based on the secondresults dataset, the first master event dataset associated with thefirst event.

In some embodiments, determining the second sub-event may includeaccessing, in the event protocol database, the first event protocol ofthe first event type, and determining the second sub-event based oncontents of the first event protocol.

In some embodiments, the computing platform may validate contents of thesecond results dataset with output data requirements specified for thesecond sub-event within the first event protocol.

In some embodiments, the computing platform may receive, via thecommunication interface, from a second event origination device, asecond event request defining a second event. Then, the computingplatform may determine a second sub-event associated with the secondevent and receive, via the communication interface, and from the eventdataset customization engine, a second customized dataset generated forthe second sub-event associated with the second event. Thereafter, thecomputing platform may generate, based on the second sub-eventassociated with the second event received from the second eventorigination device, one or more second event orchestration commandsdirecting a second sub-event processing device to execute the secondsub-event. Subsequently, the computing platform may send, via thecommunication interface, to the second sub-event processing device, thesecond customized dataset and the one or more second event orchestrationcommands directing the second sub-event processing device to execute thesecond sub-event. Then, the computing platform may receive, via thecommunication interface, from the second sub-event processing device, asecond results dataset. Thereafter, the computing platform may update,based on the second results dataset, a second master event datasetassociated with the second event.

In some embodiments, determining the second sub-event may includedetermining a second event type of the second event, accessing, in anevent protocol database, a second event protocol of the second eventtype, and determining the second sub-event based on contents of thesecond event protocol. In some instances, the computing platform may,prior to determining the second sub-event associated with the secondevent, send a command to the event dataset customization engine togenerate the second master event dataset within the event datasetcustomization engine. In some instances, the second customized datasetmay be generated in part on the second mater event dataset.

In some embodiments, the computing platform may validate contents of thesecond event request with input data requirements specified by thesecond event protocol.

In some embodiments, the computing platform may validate contents of thesecond results dataset with output data requirements specified for thesecond sub-event within the second event protocol.

In some embodiments, the computing platform may determine a thirdsub-event associated with the second event. Thereafter, the computingplatform may receive, via the communication interface and from the eventdataset customization engine, a third customized dataset generated forthe third sub-event. Then, the computing platform may generate, based onthe third sub-event associated with the second event received from thesecond event origination device, one or more third event orchestrationcommands directing a third sub-event processing device to execute thethird sub-event. Subsequently, the computing platform may send, via thecommunication interface and via an external event processing interface,to the third sub-event processing device, the third customized datasetand the one or more third event orchestration commands directing thethird sub-event processing device to execute the third sub-event.Thereafter, the computing platform may receive, via the communicationinterface and via the external event processing interface, from thethird sub-event processing device, a third results dataset. Then, thecomputing platform may update, based on the third results dataset, thesecond master event dataset associated with the second event. In someinstances, determining the third sub-event may include accessing, in theevent protocol database, the second event protocol of the second eventtype and determining the third sub-event based on contents of the secondevent protocol.

These features, along with many others, are discussed in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIGS. 1A and 1B depict an illustrative computing environment formulticomputer processing of an event request from an event originationdevice with centralized event orchestration in accordance with one ormore example embodiments;

FIGS. 2A-2H depict an illustrative event sequence for multicomputerprocessing of an event request from an event origination device withcentralized event orchestration in accordance with one or more exampleembodiments;

FIGS. 3-4 depict example graphical user interfaces for multicomputerprocessing of an event request from an event origination device withcentralized event orchestration in accordance with one or more exampleembodiments; and

FIG. 5 depicts an illustrative method for multicomputer processing of anevent request from an event origination device with centralized eventorchestration in accordance with one or more example embodiments.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments,reference is made to the accompanying drawings, which form a parthereof, and in which is shown, by way of illustration, variousembodiments in which aspects of the disclosure may be practiced. It isto be understood that other embodiments may be utilized, and structuraland functional modifications may be made, without departing from thescope of the present disclosure.

It is noted that various connections between elements are discussed inthe following description. It is noted that these connections aregeneral and, unless specified otherwise, may be direct or indirect,wired or wireless, and that the specification is not intended to belimiting in this respect.

Some aspects of the disclosure relate to orchestrating, in response toreceiving an event orchestration request to orchestrate an event,execution of a sequence of sub-events between one or more independentcomputing systems. The event orchestration request may be received froma computing device within a financial institution, or from an externalcomputing device associated with an organization, such as a treasuryclient of a financial institution, or by an individual, such as acustomer of a financial institution. The data processing capabilities ofeach of the one or more independent computing systems may vary.Accordingly, a master event dataset may be created for the event, andindividual customized datasets may be generated and transmitted to eachof the one or more independent computing systems. Each of the one ormore independent computing devices may then execute one or moresub-events using a customized dataset.

FIGS. 1A and 1B depict an illustrative computing environment formulticomputer processing of an event request from an event originationdevice with centralized event orchestration in accordance with one ormore example embodiments. Referring to FIG. 1A, computing environment100 may include one or more computing devices and/or other computersystems. For example, computing environment 100 may include an eventorchestration computing platform 110, an event dataset customizationengine 120, an event recording computing platform 130, an external eventprocessing interface 140, a first external sub-event processor 150, asecond external sub-event processor 155, a first event originationdevice 160, a second event origination device 165, a first sub-eventprocessor 170, and a second sub-event processor 175.

Event orchestration computing platform 110 may be configured toorchestrate events that are defined and/or requested by one or moreevent origination devices, control and/or direct actions of otherdevices and/or computer systems (e.g., in orchestrating events that aredefined and/or requested by one or more event origination devices and/orin performing other actions), and/or perform other functions, asdiscussed in greater detail below. Event orchestration computingplatform 110 may include event protocol database 116. Eventorchestration computing platform 110 may be configured to orchestrate aplurality of different types of events. Each type of event may beassociated with an event protocol comprising a specific sequence ofsub-events, and different rules and/or parameters for the event and/orone or more sub-events of the event. Event orchestration computingplatform 110 may store each of these event protocols in event protocoldatabase 116.

Event dataset customization engine 120 may be configured to generate oneor more event customized datasets 121 that are provided to othercomputer systems and/or devices in computing environment 100, includingexternal event processing interface 140, external sub-event processor150, external sub-event processor 155, sub-event processor 170, andsub-event processor 175. Event dataset customization engine 120 mayfurther be configured to generate, for each event orchestrated by eventorchestration computing platform 110, a master event dataset 122. Eachmaster event dataset 122 stored in event dataset customization engine120 may adhere to a universal event standard. The standard and/or formatof each event customized dataset 121 may vary based on the capabilitiesof the computing device (i.e. sub-event processor 170, sub-eventprocessor 175, external sub-event processor 150, and/or externalsub-event processor 155) that will be utilizing that event customizeddataset. In some instances, the one or more customized datasets that aregenerated by event dataset customization engine 120 may be served tosuch other computer systems and/or devices by event orchestrationcomputing platform 110, as illustrated in greater detail below. Eventrecording computing platform 130 may be configured to store, maintain,and/or update one or more records associated with one or more eventsoccurring in computing environment 100, including one or more eventsorchestrated by event orchestration computing platform 110 and/orotherwise associated with event orchestration computing platform 110.

External event processing interface 140 may be configured to facilitateprocessing of one or more events that are orchestrated by eventorchestration computing platform 110 and/or otherwise associated withevent orchestration computing platform 110 and that may be performed byand/or involve one or more external sub-event processors, such asexternal sub-event processor 150 and external sub-event processor 155.For example, event orchestration computing platform 110 may be operatedby and/or otherwise associated with a particular organization (e.g., afinancial institution) and may, in some instances, be configured toorchestrate and/or control one or more events (e.g., financialtransactions such as a payment and/or a transfer of currency). Inaddition, external sub-event processor 150 and external sub-eventprocessor 155 may, for example, be operated by and/or otherwiseassociated with one or more other organizations (e.g., paymentprocessors, credit networks, debit networks, digital wallet services,and/or the like) different from the particular organization operatingevent orchestration computing platform 110 (e.g., different from thefinancial institution operating event orchestration computing platform110). In some instances, external event processing interface 140 may beprovided with and/or include one or more dedicated communication linksand/or dedicated communication channels, which may directly and/orsecurely connect external event processing interface 140 to the one ormore external event processors, including external sub-event processor150 and/or external sub-event processor 155.

External sub-event processor 150 may be operated by and/or configured toprocess events associated with a first service provider or entity, suchas a payment processor, a credit network, a debit network, a digitalwallet service, and/or the like. External sub-event processor 155 may beoperated by and/or configured to process events associated with a secondservice provider or entity, such as a payment processor, a creditnetwork, a debit network, a digital wallet service, and/or the like,different from the first service provider. Alternatively, externalsub-event processor 150 and external sub-event processor 155 may both beoperated by and/or configured to process events associated with a sameservice provider or entity. Event origination device 160 may beconfigured to be used by an individual associated with an organization,such as an employee of a financial institution. Event origination device165 may be configured to be used by a first customer of an organization,such as a commercial client or treasury client of a financialinstitution.

In one or more arrangements, event dataset customization engine 120,event recording computing platform 130, external event processinginterface 140, external sub-event processor 150, external sub-eventprocessor 155, event origination device 160, event origination device165, sub-event processor 170, and sub-event processor 175 may be anytype of computing device capable of receiving a user interface,receiving input via the user interface, and communicating the receivedinput to one or more other computing devices. For example, event datasetcustomization engine 120, event recording computing platform 130,external event processing interface 140, external sub-event processor150, external sub-event processor 155, event origination device 160,event origination device 165, sub-event processor 170, and sub-eventprocessor 175 may, in some instances, be and/or include servercomputers, desktop computers, laptop computers, tablet computers, smartphones, or the like that may include one or more processors, memories,communication interfaces, storage devices, and/or other components. Asnoted above, and as illustrated in greater detail below, any and/or allof event dataset customization engine 120, event recording computingplatform 130, external event processing interface 140, externalsub-event processor 150, external sub-event processor 155, eventorigination device 160, event origination device 165, sub-eventprocessor 170, and sub-event processor 175 may, in some instances, bespecial-purpose computing devices configured to perform specificfunctions.

Computing environment 100 also may include one or more computingplatforms. For example, and as noted above, computing environment 100may include event orchestration computing platform 110. As illustratedin greater detail below, event orchestration computing platform 110 mayinclude one or more computing devices configured to perform one or moreof the functions described herein. For example, event orchestrationcomputing platform 110 may include one or more computers (e.g., laptopcomputers, desktop computers, servers, server blades, or the like).

Computing environment 100 also may include one or more networks, whichmay interconnect one or more of event orchestration computing platform110, event dataset customization engine 120, event recording computingplatform 130, external event processing interface 140, externalsub-event processor 150, external sub-event processor 155, eventorigination device 160, event origination device 165, sub-eventprocessor 170, and sub-event processor 175. For example, computingenvironment 100 may include private network 190 and public network 195.Private network 190 and/or public network 195 may include one or moresub-networks (e.g., local area networks (LANs), wide area networks(WANs), or the like). Private network 190 may be associated with aparticular organization (e.g., a corporation, financial institution,educational institution, governmental institution, or the like) and mayinterconnect one or more computing devices associated with theorganization. For example, event orchestration computing platform 110,event dataset customization engine 120, event recording computingplatform 130, external event processing interface 140, event originationdevice 160, event origination device 165, sub-event processor 170, andsub-event processor 175 may be associated with an organization (e.g., afinancial institution), and private network 190 may be associated withand/or operated by the organization, and may include one or morenetworks (e.g., LANs, WANs, virtual private networks (VPNs), or thelike) that interconnect event orchestration computing platform 110,event dataset customization engine 120, event recording computingplatform 130, external event processing interface 140, event originationdevice 160, event origination device 165, sub-event processor 170, andsub-event processor 175 and one or more other computing devices and/orcomputer systems that are used by, operated by, and/or otherwiseassociated with the organization. Public network 195 may connect privatenetwork 190 and/or one or more computing devices connected thereto(e.g., event orchestration computing platform 110, event datasetcustomization engine 120, event recording computing platform 130,external event processing interface 140, event origination device 160,event origination device 165, sub-event processor 170, and sub-eventprocessor 175) with one or more networks and/or computing devices thatare not associated with the organization. For example, externalsub-event processor 150, external sub-event processor 155, and eventorigination device 165 might not be associated with an organization thatoperates private network 190 (e.g., because external sub-event processor150, external sub-event processor 155, and event origination device 165may be owned, operated, and/or serviced by one or more entitiesdifferent from the organization that operates private network 190, suchas one or more customers of the organization and/or vendors of theorganization, rather than being owned and/or operated by theorganization itself or an employee or affiliate of the organization),and public network 195 may include one or more networks (e.g., theinternet) that connect external sub-event processor 150, externalsub-event processor 155, and event origination device 165 to privatenetwork 190 and/or one or more computing devices connected thereto(e.g., event orchestration computing platform 110, event datasetcustomization engine 120, event recording computing platform 130,external event processing interface 140, event origination device 160,event origination device 165, sub-event processor 170, and sub-eventprocessor 175).

Referring to FIG. 1B, event orchestration computing platform 110 mayinclude one or more processors 111, memory 112, and communicationinterface 115. A data bus may interconnect processor(s) 111, memory 112,and communication interface 115. Communication interface 115 may be anetwork interface configured to support communication between eventorchestration computing platform 110 and one or more networks (e.g.,private network 190, public network 195, or the like). Memory 112 mayinclude one or more program modules having instructions that whenexecuted by processor(s) 111 cause event orchestration computingplatform 110 to perform one or more functions described herein and/orone or more databases that may store and/or otherwise maintaininformation which may be used by such program modules and/orprocessor(s) 111. In some instances, the one or more program modulesand/or databases may be stored by and/or maintained in different memoryunits of event orchestration computing platform 110 and/or by differentcomputing devices that may form and/or otherwise make up eventorchestration computing platform 110. For example, memory 112 may have,store, and/or include an event orchestration module 113 and an eventorchestration database 114. Event orchestration module 113 may haveinstructions that direct and/or cause event orchestration computingplatform 110 to orchestrate one or more events involving one or moreother computing devices and/or computer systems in computing environment100 and/or perform other functions, as discussed in greater detailbelow. Event orchestration database 114 may store information used byevent orchestration module 113 and/or event orchestration computingplatform 110 in orchestrating one or more events involving one or moreother computing devices and/or computer systems in computing environment100 and/or in performing other functions. For example, eventorchestration database 114 may store, in part, one or more eventcustomized datasets and one or more master event datasets.

FIGS. 2A-2H depict an illustrative event sequence for multicomputerprocessing of an event request from an event origination device withcentralized event orchestration in accordance with one or more exampleembodiments. Referring to FIG. 2A, at step 201, event orchestrationcomputing platform 110 may receive a first event request from eventorigination device 160 to orchestrate a first event. For example, atstep 201, event orchestration computing platform 110 may receive amessage from event origination device 160 requesting the orchestrationof a first event by event orchestration computing platform 110. In oneexample, the first event may be a financial transaction event, such as apayment or a transferal of currency. The first event request may includeone or more associated event parameters. For example, the first eventrequest may specify an event type parameter associated with the firstevent, an event date parameter associated with the first event, an eventoccurrence parameter associated with the first event, and additionalrelevant parameters. The event date parameter may specify the date onwhich event orchestration computing platform 110 is to commenceorchestration of the first event. The event occurrence parameter mayspecify whether orchestration of the first event is to occur on aone-time basis or on a repeated basis. If orchestration of the firstevent is to occur on a repeated basis, the event occurrence parametermay specify the frequency for which the first event is to beorchestrated (i.e. daily, weekly, monthly, and the like). The firstevent request may further include one or more datasets needed fororchestration of the first event. For example, the first event requestmay include information specifying one or more sources of data fororchestration of the first event (such as one or more financial accountsand/or computing systems) and one or more destinations of data fororchestration of the first event (such as one or more financial accountsand/or computing systems).

In one example, event orchestration computing platform 110 may receivethe first event request from a user interface presented on eventorigination device 160. An example of a graphical user interface thatmay be displayed on event origination device 160 for the purposes ofgenerating and transmitting event requests is shown in FIG. 3. As seenin FIG. 3, graphical user interface 300 may include one or more fields,controls, and/or other elements that may allow a user of eventorigination device 160 to define a new event, such as a financialtransaction, to be orchestrated by event orchestration computingplatform 110. For example, graphical user interface 300 may include oneor more fields, controls, and/or other elements that may allow a user ofevent origination device 160 to specify and/or otherwise define an eventdate parameter associated with the event, an event type parameterassociated with the event, an event occurrence parameter associated withthe event, and/or other parameters associated with the event. Inaddition, and as seen in FIG. 3, graphical user interface 300 mayinclude one or more fields, controls, and/or other elements that mayallow a user of event origination device 160 to include datasets to beused by event orchestration computing platform 110 in orchestrating theevent. In one example, a user of graphical user interface 300 may enterthe datasets directly into graphical user interface 300, and thedatasets themselves may be transmitted in the event request. In anotherexample, a user of graphical user interface 300 may specify thelocation(s) of one or more datasets to be utilized by eventorchestration computing platform 110. Event orchestration computingplatform 110 may then access the dataset(s) at the specified location(s)during the orchestration of the event. Specifying the location(s) of thedataset(s) may eliminate the need to transmit large amounts of data overthe communication channels between event origination device 160 andevent orchestration computing platform 110.

Returning to FIG. 2A, at step 202, event orchestration computingplatform 110 may determine the event type of the first event. Asdiscussed above in reference to FIG. 3, an event type parameter may beincluded in the event request. Event orchestration computing platform110 may determine the event type by extracting the event type parameterfrom the received event request. For example, at step 202, eventorchestration computing platform 110 may determine that the first eventis associated with a first event type.

Responsive to determining the event type for the first event, eventorchestration computing platform 110 may validate the contents of thefirst event request received from event origination device 160. Eventorchestration computing platform 110 may include an event protocoldatabase 116 that stores a different set of protocols for each differenttype of event that may be orchestrated by event orchestration computingplatform 110. Each event protocol may include a specification of thedata that must be included in an event request to orchestrate events ofthat event type. For example, the first event protocol for the firstevent type may include a specification of the datasets that must beincluded in an event request for orchestration of an event of the firstevent type. Event orchestration computing platform 110 may validate thefirst event request by comparing the dataset(s) in the first eventrequest to the dataset(s) specified in the first event protocol. If theevent orchestration computing platform 110 successfully validates thefirst event request (i.e. the first event request includes thedataset(s) specified in the first event protocol for the first eventtype), event orchestration computing platform 110 may proceed to thenext step. If event orchestration computing platform 110 determines thatone or more required datasets have been omitted in the event request,event orchestration computing platform 110 may send a notification toevent origination device 160 indicating that the first event requestcannot be completed. Alternatively, if event orchestration computingplatform 110 determines that one or more required datasets have beenomitted in the event request, event orchestration computing platform 110may send a request for the omitted data to event origination device 160.Once event orchestration computing platform 110 receives the omitteddata from event origination device 160, event orchestration computingplatform 110 may proceed to the next step.

At step 203, event orchestration computing platform 110 may transmit oneor more commands to event dataset customization engine 120. The one ormore commands may instruct event dataset customization engine 120 togenerate a master event dataset for the first event. As noted above,event orchestration computing platform 110 may include an event protocoldatabase 116 that stores a different set of protocols for each differenttype of event that may be orchestrated by event orchestration computingplatform 110. Each event protocol may include, in part, a framework forthe master event dataset that is to be generated for each event requestfor an event of the event type corresponding to that event protocol. Theframework may enumerate one or more parameters and/or datasets to becreated within the master event dataset.

For example, event orchestration computing platform 110 may beconfigured to orchestrate at least two different event types, a firstillustrative event type and a second illustrative event type. The firstillustrative event type may be associated with a first illustrativeevent protocol (including a first illustrative framework for a masterevent dataset) within event protocol database 116 and the secondillustrative event type may be associated with a second illustrativeevent protocol (including a second illustrative framework for a masterevent dataset) within event protocol database 116. Event orchestrationcomputing platform 110 may receive a first illustrative request toorchestrate a first illustrative event and a second illustrative requestto orchestrate a second illustrative event. In a first instance, thefirst illustrative event and the second illustrative event may both beof the first illustrative event type. Accordingly, in the firstinstance, event orchestration computing platform 110 may utilizecontents of the first illustrative framework specified in the firstillustrative event protocol for the first illustrative event type togenerate one or more commands instructing event dataset customizationengine 120 to generate a first illustrative master dataset for the firstillustrative event. Further in the first instance, event orchestrationcomputing platform 110 may utilize contents of the first illustrativeframework specified in the first illustrative event protocol for thefirst illustrative event type to generate one or more commandsinstructing event dataset customization engine 120 to generate a secondillustrative master dataset for the second illustrative event. In asecond instance, the first illustrative event may be of the firstillustrative event type and the second illustrative event may be of thesecond illustrative event type. Accordingly, in the second instance,event orchestration computing platform 110 may utilize contents of thefirst illustrative framework specified in the first illustrative eventprotocol for the first illustrative event type to generate one or morecommands instructing event dataset customization engine 120 to generatea first illustrative master dataset for the first illustrative event.Further in the second instance, event orchestration computing platform110 may utilize contents of the second illustrative framework specifiedin the second illustrative event protocol for the second illustrativeevent type to generate one or more commands instructing event datasetcustomization engine 120 to generate a second illustrative masterdataset for the second illustrative event.

Therefore, to generate the one or more commands to be transmitted toevent dataset customization engine 120 for the first event in the firstevent request received at step 201, event orchestration computingplatform 110 may access a first event protocol associated with the firstevent type determined at step 202. Event orchestration computingplatform 110 may then generate the one or more commands based on a firstframework for the event master dataset specified in the first eventprotocol. For example, the one or more commands generated by eventorchestration computing platform 110 may include the parameters and/ordatasets enumerated in the first framework for the event master dataset.Alternatively, the one or more commands may include a storage locationof the first event protocol (or the first framework for the master eventdataset) for the first event type so that event dataset customizationengine 120 may directly access the first framework when subsequentlygenerating the master event dataset for the first event.

At step 204, event orchestration computing platform 110 may determine afirst sub-event associated with the first event. As noted above, eventorchestration computing platform 110 may include an event protocoldatabase 116 that stores a different set of protocols for each differenttype of event that may be orchestrated by event orchestration computingplatform 110. Each event protocol may include, in part, a sequence ofsub-events that are to be executed in order to complete orchestration ofan event of the event type associated with that event protocol. Forexample, the first event protocol for the first event type may specify afirst sequence of sub-events that are to be executed for each event ofthe first event type. Each sub-event of the first sequence may beexecuted by a different sub-event processor (i.e. sub-event processor170, sub-event processor 175, external sub-event processor 150, externalsub-event processor 155.) To determine the first sub-event associatedwith the first event, event orchestration computing platform 110 mayaccess the first event protocol associated with the first event type,and subsequently identify the first sub-event listed in the firstsequence of sub-events. For example, the first event may be a paymenttransaction, and the first sub-event may be unauthorized use analysis ofthe payment, sanctions analysis of the payment, a clearing of thepayment, a settlement of funds associated with the payment, and thelike.

At step 205, event orchestration computing platform 110 may send one ormore commands to event dataset customization engine 120 to generate acustomized dataset to be utilized for execution of the first sub-event.As noted above, each event protocol may include, in part, a sequence ofsub-events that are to be executed in order to complete orchestration ofan event of the event type associated with that event protocol. Eachevent protocol may further include one or rules for each sub-event inthe sequence of sub-events. For each sub-event, the rules may specifythe computing device that is to execute the sub-event. For eachsub-event, the rules may further specify one or more command(s) to besent to the computing device that is to execute the sub-event. For eachsub-event, the rules may further specify the contents of a customizeddataset that is to be utilized by the computing device when executingthe sub-event. The contents of the customized dataset may be determinedbased on the data requirements for the sub-event and the capabilities ofthe computing device that is to execute the sub-event. For example, therules for the first sub-event identified in step 204 may indicate thatthe first sub-event is to be executed by sub-event processor 170. Therules may further specify that execution of the first sub-event onlyrequires a first subset of the data stored in the first master eventdataset generated for the first event. It may be advantageous totransmit only the required data (i.e. the first subset of data) tosub-event processor 170 to reduce network traffic (i.e. bandwidthusage). Additionally, in one example, sub-event processor 170 may be alegacy computing system. In this case, it may be necessary to convertthe first subset of data into a different format that may be processedby sub-event processor 170. Accordingly, event orchestration computingplatform 110 may generate one or more commands instructing event datasetcustomization engine 120 to generate a first event customized datasetfor the first sub-event that includes the first subset of data from themaster event dataset stored in event dataset customization engine 120for the first event. Additionally, event orchestration computingplatform 110 may generate one or more commands instructing event datasetcustomization engine 120 to further convert the first subset of datainto a specified format (i.e. a format that may be utilized by sub-eventprocessor 170 when executing the first sub-event). Event orchestrationcomputing platform 110 may then send the generated one or more commandsto event dataset customization engine 120.

Referring to FIG. 2B, at step 206, event orchestration computingplatform 110 may receive the first event customized dataset for thefirst sub-event from event dataset customization engine 120. Eventdataset customization engine 120 may have generated the first eventcustomized dataset for the first sub-event by extracting the requestedfirst subset of data from the first event master dataset generated forthe first event. Event dataset customization engine 120 may then haveperformed the conversion of the first subset data to the format requiredby sub-event processor 170 or may have utilized a separate conversionengine (not shown). Alternatively, event orchestration computingplatform 110 may receive the storage location of the first eventcustomized dataset for the first sub-event from event datasetcustomization engine 120.

At step 207, event orchestration computing platform 110 may send one ormore event orchestration commands and supplementary data to sub-eventprocessor 170. For example, event orchestration computing platform 110may sent one or more event orchestration commands specified in the rulesfor the first sub-event in the first event protocol and the first eventcustomized dataset for the first sub-event to sub-event processor 170.The one or more event orchestration commands may be generated based onthe commands specified in the rules for the first sub-event in the firstevent protocol. In one scenario, event orchestration computing platform110 may send the storage location of the supplementary data to sub-eventprocessor 170 in place of sending the supplementary data in itsentirety. For example, event orchestration computing platform 110 maysend the storage location of the first event customized dataset for thefirst sub-event to sub-event processor 170. Sending the storage locationof the first event customized dataset for the first sub-event instead ofthe first event customized dataset for the first sub-event in itsentirety reduces the traffic sent on the communication channels betweenevent orchestration computing platform 110 and sub-event processor 170and thus provides technical benefits and operational advantages.

At step 208, event orchestration computing platform 110 may receive afirst results dataset from sub-event processor 170. For example, eventorchestration computing platform 110 may receive a first results datasetfrom sub-event processor 170 that may include data generated bysub-event processor 170 during, or as a result of, execution of thefirst sub-event. At step 209, event orchestration computing platform 110may validate the first results dataset received from sub-event processor170. In validating the first results dataset, event orchestrationcomputing platform 110 may access the one or more rules defined for thefirst sub-event within the first event protocol associated with thefirst event type. The one or more rules defined for the first sub-eventmay include information defining the data that is to be received fromthe sub-event processor 170 as a result of the sub-event processor 170executing the first sub-event. Event orchestration computing platform110 may compare the information in the one or more rules to the firstresults dataset received from the sub-event processor 170. If thevalidation indicates that the correct data is included in the firstresults dataset, event orchestration computing platform 110 may proceedto the next step. If there is an error within the first results dataset,event orchestration computing platform 110 may transmit a notificationto sub-event processor 170 indicating that the first sub-event should bere-executed by sub-event processor 170. Alternatively, eventorchestration computing platform 110 may transmit a request for theomitted data to sub-event processor 170.

Turning to FIG. 2C, at step 210, event orchestration computing platform110 may update the first event master dataset generated for the firstevent. For example, event orchestration computing platform 110 mayupdate the first event master dataset generated for the first eventbased on the data in the validated first results dataset. If the firstresults dataset includes updated values for parameters already stored inthe first event master dataset, event orchestration computing platform110 may replace the current values of these parameters in the firstevent master dataset with the updated values. If the first resultsdataset includes new parameters and values that are not currently in thefirst event master dataset, these new parameters and values may be addedto the first event master dataset.

At step 211, event orchestration computing platform 110 may determine asecond sub-event associated with the first event. In determining thesecond sub-event associated with the first event, event orchestrationcomputing platform 110 may access the first event protocol associatedwith the first event type (i.e. the event type of the first event).Event orchestration computing platform 110 may identify, within thefirst event protocol, the second sub-event listed in the first sequenceof sub-events. For example, the first event may be a paymenttransaction, and the second sub-event may be unauthorized use analysisof the payment, sanctions analysis of the payment, a clearing of thepayment, a settlement of funds associated with the payment, and thelike. In other embodiments, a second sub-event associated with the firstevent may be determined from the first results dataset. For example, thefirst results dataset may include an indication of the second sub-event.In another example, the first results dataset may include data directingevent orchestration computing platform 110 to a specific sub-event inthe first event protocol that is to be executed as the second sub-event.Utilizing data from the first results dataset to determine the secondsub-event for the first event allows for a flexible execution of thefirst event protocol. For example, execution of one or more sub-eventsin the first event protocol may be bypassed based on the contents of thefirst results dataset, therefore resulting in an execution of only asubset of the sub-events listed in the first event protocol in certaininstances.

At step 212, event orchestration computing platform 110 may send one ormore commands to event dataset customization engine 120 to generate acustomized dataset to be utilized for execution of the second sub-eventassociated with the first event. As noted above, each event protocol mayinclude, in part, a sequence of sub-events that are to be executed inorder to complete orchestration of each event of that event type. Eachof the event protocols may further include one or rules for eachsub-event, wherein the rules may specify the computing device that is toexecute the sub-event, one or more command(s) to be sent to thecomputing device that is to execute the sub-event, and the contents of acustomized dataset that is to be utilized by the computing device whenexecuting the sub-event. The contents of the customized dataset may bedetermined based on the data requirements for execution of the sub-eventand the capabilities of the computing device that is to execute thesub-event. For example, the rules for the second sub-event identified instep 211 may indicate that the second sub-event associated with thefirst event is to be executed by external sub-event processor 150.External sub-event processor 150 may be operated by and/or configured toprocess events associated with a first service provider or entity, suchas a payment processor, a credit network, a debit network, a digitalwallet service, and/or the like. The rules for the second sub-eventassociated with the first event may further specify that execution ofthe second sub-event associated with the first event only requires asecond subset of the data stored in the first master event datasetgenerated for the first event. It may be advantageous to transmit onlythe required data (i.e. the second subset of data) to external sub-eventprocessor 150 to reduce network traffic (i.e. bandwidth usage) and/or toreduce the amount of data exposed to potential security risks. In oneexample, external sub-event processor 150 may be a legacy computingsystem (such as a legacy computing server) or a different type ofcomputing system. In this case, it may be necessary to convert thesecond subset of data into a different format that may be processed byexternal sub-event processor 150. Accordingly, event orchestrationcomputing platform 110 may generate one or more commands instructingevent dataset customization engine 120 to generate a second eventcustomized dataset for the second sub-event associated with the firstevent that includes the second subset of data from the first masterevent dataset stored in event dataset customization engine 120. Eventorchestration computing platform 110 may further generate one or morecommands instructing event dataset customization engine 120 to convertthe second subset of data into a specified format (i.e. a format thatmay be required by external sub-event processor 150). Eventorchestration computing platform 110 may then send the generated one ormore commands to event dataset customization engine 120.

At step 213, event orchestration computing platform 110 may receive thesecond event customized dataset for the second sub-event associated withthe first event from event dataset customization engine 120. Eventdataset customization engine 120 may have generated the second eventcustomized dataset for the first event by extracting the requestedsecond subset of data from the first event master dataset generated forthe first event. Event dataset customization engine 120 may then haveperformed the conversion of the second subset of data to the formatrequired by external sub-event processor 150 or may have utilized aseparate conversion engine (not shown). Alternatively, eventorchestration computing platform 110 may receive the storage location ofthe second event customized dataset for the second sub-event associatedwith the first event from event dataset customization engine 120.

Turning to FIG. 2D, at step 214, event orchestration computing platform110 may send the second event customized dataset and one or more eventorchestration commands specified in the rules for the second sub-eventassociated with the first event to external sub-event processor 150. Forexample, event orchestration computing platform 110 may send the secondevent customized dataset generated for the second sub-event associatedwith the first event and one or more event orchestration commandsspecified in the rules for the second sub-event to external sub-eventprocessor 150 via external event processing interface 140. Eventorchestration computing platform 110 may generate the one or more eventorchestration commands based on the commands specified in the rules forthe second sub-event associated with the first event in the firstsequence of sub-events in the first event protocol. Alternatively, eventorchestration computing platform 110 may send the storage location ofthe second event customized dataset for the second sub-event associatedwith the first event to external sub-event processor 150. Sending thestorage location of the second event customized dataset instead of thesecond event customized dataset in its entirety may reduce the trafficsent on the communication channels between event orchestration computingplatform 110 and external sub-event processor 150.

At step 215, event orchestration computing platform 110 may receive asecond results dataset from external sub-event processor 150. The secondresults dataset may include data generated by external sub-eventprocessor 150 during, or as a result of, execution of the secondsub-event. At step 216, event orchestration computing platform 110 mayvalidate the second results dataset received from external sub-eventprocessor 150. In validating the second results dataset received fromexternal sub-event processor 150, event orchestration computing platform110 may access the one or more rules defined for the second sub-eventassociated with the first event within the first event protocolassociated with the first event type (i.e. the event type of the firstevent). The one or more rules defined for the second sub-eventassociated with the first event may include information defining thedata that is to be received from external sub-event processor 150 as aresult of external sub-event processor 150 executing the secondsub-event associated with the first event. Event orchestration computingplatform 110 may compare the information in the one or more rulesdefined for the second sub-event associated with the first event withinthe first event protocol associated with the first event type to thesecond results dataset received from external sub-event processor 150.If the validation indicates that the correct data is included in thesecond results dataset, event orchestration computing platform 110 mayproceed to the next step. If there is an error within the second resultsdataset, event orchestration computing platform 110 may transmit anotification to external sub-event processor 150 indicating that thesecond sub-event associated with the first event should be re-executedby external sub-event processor 150. Alternatively, event orchestrationcomputing platform 110 may transmit a request for the omitted data toexternal sub-event processor 150.

At step 217, event orchestration computing platform 110 may update thefirst event master dataset generated for the first event. For example,event orchestration computing platform 110 may update the first mastergenerated for the first event based on the data in the validated secondresults dataset. If the second results dataset includes updated valuesfor parameters that are already in the first event master dataset, eventorchestration computing platform 110 may replace the current values ofthese parameters in the first event master dataset with the updatedvalues. If the second results dataset includes new parameters andvalues, event orchestration computing platform 110 may add these newparameters and values to the first event master dataset.

At step 218, event orchestration computing platform 110 may update oneor more master records associated with the first event. For example,event orchestration computing platform 110 may update one or more masterrecords associated with the first event and stored in event recordingcomputing platform 130 upon determining that orchestration of the firstevent is complete. Event orchestration computing platform 110 maydetermine that orchestration of the first event is complete based on thecontents of the first event protocol associated with the first event. Asnoted above, the first event protocol may include a sequence ofsub-events that must be executed in order to complete orchestration ofevents of the first event type, such as the first event. Each of thesub-events in the sequence of sub-events may include one or more rules.The one or more rules of the last sub-event in the sequence ofsub-events for the first event protocol may include an indication thatonce the last sub-event has been executed, no further sub-events need tobe executed for events of the first event type. In other embodiments,one or more rules of the last sub-event in the sequence of sub-eventsfor the first event protocol may include an indication that once thelast sub-event has been executed, event orchestration of another eventis to be triggered, thus resulting in a recursive orchestration ofevents. Accordingly, once event orchestration computing platform 110 hasupdated the first event master dataset after execution of the secondsub-event, event orchestration computing platform 110 may determine thatthe second sub-event is the last sub-event in the sequence of sub-eventsfor the first event protocol. Accordingly, event orchestration computingplatform 110 may update one or more master records associated with thefirst event and stored in event recording computing platform 130 toindicate that orchestration of the first event has been completed. Eventorchestration computing platform 110 may update the one or more masterrecords associated with the first event and stored in event recordingcomputing platform 130 to further indicate the completion date and/ortime of orchestration of the first event. Event orchestration computingplatform 110 may update the one or more master records associated withthe first event and stored in event recording computing platform 130 toinclude the contents or storage location of the first event masterdataset.

Referring to FIG. 2E, at step 219, event orchestration computingplatform 110 may receive a second event request from event originationdevice 165 to orchestrate a second event. For example, at step 219,event orchestration computing platform 110 may receive a message fromevent origination device 165 requesting the orchestration of a secondevent by event orchestration computing platform 110. In one example, thesecond event may be a financial transaction event. The second eventrequest may include one or more associated event parameters. Forexample, the second event request may specify an event type parameterassociated with the second event, an event date parameter associatedwith the second event, an event occurrence parameter associated with thesecond event, and additional relevant parameters. The event dateparameter may specify the date on which event orchestration computingplatform 110 is to commence orchestration of the second event. The eventoccurrence parameter may specify whether orchestration of the secondevent is to occur on a one-time basis or on a repeated basis. Iforchestration of the second event is to occur on a repeated basis, theevent occurrence parameter may specify the frequency for which thesecond event is to be orchestrated (i.e. daily, weekly, monthly, and thelike). The second event request may further include one or more datasetsneeded for orchestration of the second event. For example, the secondevent request may include information specifying one or more sources ofdata for orchestration of the second event (such as one or morefinancial accounts and/or computer systems) and one or more destinationsof data for orchestration of the second event (such as one or morefinancial accounts and/or computer systems).

In one example, event orchestration computing platform 110 may receivethe second event request from a user interface presented on eventorigination device 165. An example of a graphical user interface thatmay be displayed on event origination device 165 for the purposes ofgenerating and transmitting event requests is shown in FIG. 4. As seenin FIG. 4, graphical user interface 400 may include one or more fields,controls, and/or other elements that may allow a user of eventorigination device 165 to define a new event, such as a financialtransaction, to be orchestrated by event orchestration computingplatform 110. For example, graphical user interface 400 may include oneor more fields, controls, and/or other elements that may allow a user ofevent origination device 165 to specify and/or otherwise define an eventdate parameter associated with the event, an event type parameterassociated with the event, an event occurrence parameter associated withthe event, and/or other parameters associated with the event. Inaddition, and as seen in FIG. 4, graphical user interface 400 mayinclude one or more fields, controls, and/or other elements that mayallow a user of event origination device 165 to include datasets to beused by event orchestration computing platform 110 in orchestrating theevent. In one example, a user of graphical user interface 400 may enterthe datasets directly into graphical user interface 400, and thedatasets themselves may be transmitted in the event request. In anotherexample, a user of graphical user interface 400 may specify thelocation(s) of one or more datasets to be utilized by eventorchestration computing platform 110. Event orchestration computingplatform 110 may then access the dataset(s) at the specified location(s)during the orchestration of the event. Specifying the location(s) of thedataset(s) may eliminate the need to transmit large amounts of data overthe communication channels between event origination device 165 andevent orchestration computing platform 110.

Returning to FIG. 2E, at step 220, event orchestration computingplatform 110 may determine the event type of the second event. Asdiscussed above in reference to FIG. 4, an event type parameter may beincluded in event request received from event origination device 165.Event orchestration computing platform 110 may determine the event typeof the second event by extracting the event type parameter from thesecond event request. For example, at step 220, event orchestrationcomputing platform 110 may determine that the second event is associatedwith a second event type.

Responsive to determining the event type for the second event, eventorchestration computing platform 110 may validate the contents of thesecond event request received from event origination device 165. Asnoted above, event orchestration computing platform 110 may include anevent protocol database 116 that stores a different event protocol foreach different type of event that may be orchestrated by eventorchestration computing platform 110. As further noted above, each eventprotocol may include a specification of the data that must be includedin an event request of the corresponding event type. For example, eventorchestration computing platform 110 may store a second event protocolthat is associated with the second event type. The second event protocolassociated with the second event type may include a specification of thedatasets that must be included in an event request for orchestration ofan event of the second event type. Event orchestration computingplatform 110 may validate the second event request by comparing thedataset(s) in the second event request to the dataset(s) specified inthe second event protocol. If the event orchestration computing platform110 successfully validates the second event request (i.e. the secondevent request includes the dataset(s) specified in the second eventprotocol for the second event type), event orchestration computingplatform 110 may proceed to the next step. If event orchestrationcomputing platform 110 determines that one or more required datasetshave been omitted in the second event request, event orchestrationcomputing platform 110 may send a notification to event originationdevice 165 indicating that the second event request cannot be completed.Alternatively, if event orchestration computing platform 110 determinesthat one or more required datasets have been omitted in the second eventrequest, event orchestration computing platform 110 may send a requestfor the omitted data to event origination device 165. Once eventorchestration computing platform 110 receives the omitted data fromevent origination device 165, event orchestration computing platform 110may proceed to the next step.

At step 221, event orchestration computing platform 110 may transmit oneor more commands to event dataset customization engine 120. The one ormore commands may instruct event dataset customization engine 120 togenerate a second master event dataset for the second event. Asindicated above, event orchestration computing platform 110 may includean event protocol database 116 that stores a different event protocolfor each different type of event that may be orchestrated by eventorchestration computing platform 110. Each event protocol may include,in part, a framework for the master event dataset that is to begenerated for each event of the event type associated with that eventprotocol. Each framework may enumerate one or more parameters and/ordatasets to be created within the master event dataset. For example, thesecond event protocol in event protocol database 116 may store a secondframework for a second master event dataset.

Therefore, to generate the one or more commands to be transmitted toevent dataset customization engine 120 for the second event in thesecond event request received at step 219, event orchestration computingplatform 110 may access the second event protocol associated with thesecond event type determined at step 220. Event orchestration computingplatform 110 may then generate the one or more commands based on thesecond framework for the second event master dataset specified in thesecond event protocol. For example, the one or more commands generatedby event orchestration computing platform 110 may include the parametersand/or datasets enumerated in the second framework for the second eventmaster dataset. Alternatively, the one or more commands may include astorage location of the second event protocol (or the second frameworkfor the second master event dataset) for the second event type so thatevent dataset customization engine 120 may directly access the secondframework when subsequently generating the second master event datasetfor the second event.

At step 222, event orchestration computing platform 110 may determine afirst sub-event associated with the second event. As noted above, eventorchestration computing platform 110 may include an event protocoldatabase 116 that stores a different event protocol for each differenttype of event that may be orchestrated by event orchestration computingplatform 110. Each event protocol may include, in part, a sequence ofsub-events that are to be executed in order to complete orchestration ofan event of the event type associated with that event protocol. Forexample, the second event protocol for the second event type may specifya second sequence of sub-events that are to be executed for each eventof the second event type. Each sub-event of the second sequence may beexecuted by a different sub-event processor (i.e. sub-event processor170, sub-event processor 175, external sub-event processor 150, externalsub-event processor 155.) To determine the first sub-event associatedwith the second event, event orchestration computing platform 110 mayaccess the second event protocol associated with the second event type,and subsequently identify the first sub-event listed in the secondsequence of sub-events. For example, the second event may be a paymenttransaction, and the first sub-event of the second event may beunauthorized use analysis of the payment, sanctions analysis of thepayment, a clearing of the payment, a settlement of funds associatedwith the payment, and the like.

At step 223, event orchestration computing platform 110 may send one ormore commands to event dataset customization engine 120 to generate acustomized dataset to be utilized for execution of the first sub-eventof the second event. As noted above, each event protocol may include, inpart, a sequence of sub-events that are to be executed in order tocomplete orchestration of an event of the event type associated withthat event protocol. Each event protocol may further include one orrules for each sub-event in the sequence of sub-events. For example, thesecond sequence of sub-events in second event protocol may include, foreach sub-event therein, the computing device that is to execute thesub-event, one or more command(s) to be sent to the computing devicethat is to execute the sub-event, and the contents of a customizeddataset that is to be utilized by the computing device when executingthe sub-event. The contents of the customized dataset may be determinedbased on the data requirements for the sub-event and the capabilities ofthe computing device that is to execute the sub-event. For example, therules for the first sub-event of the second event may indicate that thefirst sub-event of the second event is to be executed by sub-eventprocessor 175. The rules may further specify that execution of the firstsub-event of the second event only requires a first subset of the datastored in the second master event dataset generated for the secondevent. It may be advantageous to transmit only the required data (i.e.the first subset of data) to sub-event processor 175 to reduce networktraffic (i.e. bandwidth usage). Additionally, in one example, sub-eventprocessor 175 may be a legacy computing system. In this case, it may benecessary to convert the first subset of data into a different formatthat may be processed by sub-event processor 175. Accordingly, eventorchestration computing platform 110 may generate one or more commandsinstructing event dataset customization engine 120 to generate a firstevent customized dataset for the first sub-event of the second eventthat includes the first subset of data from the second master eventdataset stored in event dataset customization engine 120 for the secondevent. Additionally, event orchestration computing platform 110 maygenerate one or more commands instructing event dataset customizationengine 120 to further convert the first subset of data into a specifiedformat (i.e. a format that may be utilized by sub-event processor 175when executing the first sub-event of the second event). Eventorchestration computing platform 110 may then send the generated one ormore commands to event dataset customization engine 120.

Referring to FIG. 2F, at step 224, event orchestration computingplatform 110 may receive the first event customized dataset for thefirst sub-event of the second event from event dataset customizationengine 120. Event dataset customization engine 120 may have generatedthe first event customized dataset for the first sub-event of the secondevent by extracting the requested first subset of data from the secondevent master dataset generated for the second event and stored in eventdataset customization engine 120. Event dataset customization engine 120may then have converted the first subset of data into the formatrequired by sub-event processor 175 or may have utilized a separateconversion engine (not shown). Alternatively, event orchestrationcomputing platform 110 may receive the storage location of the firstevent customized dataset for the first sub-event of the second eventfrom event dataset customization engine 120.

At step 225, event orchestration computing platform 110 may send one ormore event orchestration commands and supplementary data to sub-eventprocessor 175. For example, event orchestration computing platform 110may send one or more event orchestration commands specified in the rulesfor the first sub-event of the second event in the second event protocolto sub-event processor 175 and may further send the first eventcustomized dataset for the first sub-event of the second event tosub-event processor 175. The one or more event orchestration commandsmay be generated based on the commands specified in the rules for thefirst sub-event of the second event in the second event protocol. In onescenario, event orchestration computing platform 110 may send thestorage location of the supplementary data to sub-event processor 175 inplace of sending the supplementary data in its entirety. For example,event orchestration computing platform 110 may send the storage locationof the first event customized dataset for the first sub-event of thesecond event to sub-event processor 175. Sending the storage location ofthe first event customized dataset for the first sub-event of the secondevent instead of the first event customized dataset for the firstsub-event of the second event in its entirety reduces the traffic senton the communication channels between event orchestration computingplatform 110 and sub-event processor 175.

At step 226, event orchestration computing platform 110 may receive afirst results dataset from sub-event processor 175. For example, eventorchestration computing platform 110 may receive a first results datasetfrom sub-event processor 175 that may include data generated bysub-event processor 175 during, or as a result of, execution of thefirst sub-event of the second event. At step 227, event orchestrationcomputing platform 110 may validate the first results dataset for thefirst sub-event of the second event received from sub-event processor175. In validating the first results dataset for the first sub-event ofthe second event, event orchestration computing platform 110 may accessthe one or more rules defined for the first sub-event of the secondevent within the second event protocol associated with the second eventtype. The one or more rules defined for the first sub-event of thesecond event may include information defining the data that is to bereceived from sub-event processor 175 as a result of the sub-eventprocessor 175 executing the first sub-event of the second event. Eventorchestration computing platform 110 may compare the information in theone or more rules to the first results dataset for the first sub-eventof the second event received from the sub-event processor 175. If thevalidation indicates that the correct data is included in the firstresults dataset for the first sub-event of the second event, eventorchestration computing platform 110 may proceed to the next step. Ifthere is an error within the first results dataset for the firstsub-event of the second event, event orchestration computing platform110 may transmit a notification to sub-event processor 175 indicatingthat the first sub-event of the second event should be re-executed bysub-event processor 175. Alternatively, event orchestration computingplatform 110 may transmit a request for the omitted data to sub-eventprocessor 175.

Turning to FIG. 2G, at step 228, event orchestration computing platform110 may update the second event master dataset generated for the secondevent. For example, event orchestration computing platform 110 mayupdate the second event master dataset generated for the second eventbased on the data in the validated first results dataset for the firstsub-event of the second event. If the first results dataset for thefirst sub-event of the second event includes updated values forparameters already stored in the second event master dataset, eventorchestration computing platform 110 may replace the current values ofthese parameters in the second event master dataset with the updatedvalues. If the first results dataset for the first sub-event of thesecond event includes new parameters and values that are not currentlyin the second event master dataset, event orchestration computingplatform 110 may add these new parameters and values to the second eventmaster dataset.

At step 229, event orchestration computing platform 110 may determine asecond sub-event associated with the second event. In determining thesecond sub-event associated with the second event, event orchestrationcomputing platform 110 may access the second event protocol associatedwith the second event type (i.e. the event type of the second event).Event orchestration computing platform 110 may identify, within thesecond event protocol, the second sub-event listed in the secondsequence of sub-events. For example, the second event may be a paymenttransaction, and the second sub-event may be unauthorized use analysisof the payment, sanctions analysis of the payment, a clearing of thepayment, a settlement of funds associated with the payment, and thelike. In other embodiments, a second sub-event associated with thesecond event may be determined from the second results dataset. Forexample, the second results dataset may include an indication of thesecond sub-event. In another example, the second results dataset mayinclude data directing event orchestration computing platform 110 to aspecific sub-event in the second event protocol that is to be executedas the second sub-event. Utilizing data from the second results datasetto determine the second sub-event for the second event allows for aflexible execution of the second event protocol. For example, executionof one or more sub-events in the second event protocol may be bypassedbased on the contents of the second results dataset, therefore resultingin an execution of only a subset of the sub-events listed in the secondevent protocol in certain instances.

At step 230, event orchestration computing platform 110 may send one ormore commands to event dataset customization engine 120 to generate acustomized dataset to be utilized for execution of the second sub-eventof the second event. As noted above, each event protocol may include, inpart, a sequence of sub-events that are to be executed in order tocomplete orchestration of each event of that event type. Each of theevent protocols may further include one or rules for each sub-event,wherein the rules may specify the computing device that is to executethe sub-event, one or more command(s) to be sent to the computing devicethat is to execute the sub-event, and the contents of a customizeddataset that is to be utilized by the computing device when executingthe sub-event. The contents of the customized dataset may be determinedbased on the data requirements for execution of the sub-event and thecapabilities of the computing device that is to execute the sub-event.For example, the rules for the second sub-event in the second eventprotocol may indicate that the second sub-event is to be executed byexternal sub-event processor 155. External sub-event processor 155 maybe operated by and/or configured to process events associated with asecond service provider or entity, such as a payment processor, a creditnetwork, a debit network, a digital wallet service, and/or the like. Therules for the second sub-event of the second event may further specifythat execution of the second sub-event of the second event only requiresa second subset of the data stored in the second master event datasetgenerated for the second event. It may be advantageous to transmit onlythe required data (i.e. the second subset of data) to external sub-eventprocessor 155 to reduce network traffic (i.e. bandwidth usage) and/or toreduce the amount of data exposed to potential security risks. In oneexample, external sub-event processor 155 may be a legacy computingsystem (such as a legacy computing server) or a different type ofcomputing system. In this case, it may be necessary to convert thesecond subset of data into a different format that may be processed byexternal sub-event processor 155. Accordingly, event orchestrationcomputing platform 110 may generate one or more commands instructingevent dataset customization engine 120 to generate a second eventcustomized dataset for the second sub-event of the second event thatincludes the second subset of data from the second master event datasetstored in event dataset customization engine 120. Event orchestrationcomputing platform 110 may further generate one or more commandsinstructing event dataset customization engine 120 to convert the secondsubset of data into a specified format (i.e. a format that may berequired by external sub-event processor 155). Event orchestrationcomputing platform 110 may then send the generated commands to eventdataset customization engine 120.

At step 231, event orchestration computing platform 110 may receive thesecond event customized dataset for the second sub-event of the secondevent from event dataset customization engine 120. Event datasetcustomization engine 120 may have generated the second event customizeddataset for the second sub-event of the second event by extracting therequested second subset of data from the second event master datasetgenerated for the second event. Event dataset customization engine 120may then have converted the second subset of data to the format requiredby external sub-event processor 155 or may have utilized a separateconversion engine (not shown). Alternatively, event orchestrationcomputing platform 110 may receive the storage location of the secondevent customized dataset for the second sub-event of the second eventfrom event dataset customization engine 120.

Turning to FIG. 2H, at step 232, event orchestration computing platform110 may send the second event customized dataset for the secondsub-event of the second event and one or more event orchestrationcommands specified in the rules for the second sub-event to externalsub-event processor 155. For example, event orchestration computingplatform 110 may send the second event customized dataset for the secondsub-event of the second event and one or more event orchestrationcommands specified in the rules for the second sub-event to externalsub-event processor 155 via external event processing interface 140.Event orchestration computing platform 110 may generate the one or moreevent orchestration commands based on the commands specified in therules for the second sub-event in the second sequence of sub-events inthe second event protocol. Alternatively, event orchestration computingplatform 110 may send the storage location of the second eventcustomized dataset for the second sub-event of the second event toexternal sub-event processor 155. Sending the storage location of thesecond event customized dataset for the second sub-event of the secondevent instead of the second event customized dataset for the secondsub-event of the second event in its entirety may reduce the trafficsent on the communication channels between event orchestration computingplatform 110 and external sub-event processor 155.

At step 233, event orchestration computing platform 110 may receive asecond results dataset for the second sub-event from external sub-eventprocessor 155. The second results dataset for the second sub-event mayinclude data generated by external sub-event processor 155 during, or asa result of, execution of the second sub-event of the second event. Atstep 234, event orchestration computing platform 110 may validate thesecond results dataset for the second sub-event received from externalsub-event processor 155. In validating the second results dataset forthe second sub-event, event orchestration computing platform 110 mayaccess the one or more rules defined for the second sub-event within thesecond event protocol associated with the second event type (i.e. theevent type of the second event). The one or more rules defined for thesecond sub-event may include information defining the data that is to bereceived from external sub-event processor 155 as a result of externalsub-event processor 155 executing the second sub-event. Eventorchestration computing platform 110 may compare the information in theone or more rules defined for the second sub-event within the secondevent protocol associated with the second event type to the secondresults dataset for the second sub-event received from externalsub-event processor 155. If the validation indicates that the correctdata is included in the second results dataset for the second sub-event,event orchestration computing platform 110 may proceed to the next step.If there is an error within the second results dataset for the secondsub-event, event orchestration computing platform 110 may transmit anotification to external sub-event processor 155 indicating that thesecond sub-event should be re-executed by external sub-event processor155. Alternatively, event orchestration computing platform 110 maytransmit a request for the omitted data to external sub-event processor155.

At step 235, event orchestration computing platform 110 may update thesecond event master dataset generated for the second event. For example,event orchestration computing platform 110 may update the second eventmaster dataset generated for the second event based on the data in thevalidated second results dataset for the second sub-event. If the secondresults dataset for the second sub-event includes updated values forparameters that are already in the second event master dataset, eventorchestration computing platform 110 may replace the current values ofthese parameters in the second event master dataset with the updatedvalues. If the second results dataset includes new parameters and valuesthat are not currently stored in the second event master dataset, eventorchestration computing platform 110 may add these new parameters andvalues to the second event master dataset.

At step 236, event orchestration computing platform 110 may update oneor more master records associated with the second event and stored inevent recording computing platform 130. For example, event orchestrationcomputing platform 110 may update one or more master records associatedwith the second event and stored in event recording computing platform130 upon determining that orchestration of the second event is complete.Event orchestration computing platform 110 may determine thatorchestration of the second event is complete based on the contents ofthe second event protocol associated with the second event. As notedabove, the second event protocol may include a sequence of sub-eventsthat must be executed in order to complete orchestration of events ofthe second event type, such as the second event. Each of the sub-eventsin the sequence of sub-events may include one or more rules. The one ormore rules of the last sub-event in the sequence of sub-events for thesecond event protocol may include an indication that once the lastsub-event has been executed, no further sub-events need to be executedfor events of the second event type. In other embodiments, one or morerules of the last sub-event in the sequence of sub-events for the secondevent protocol may include an indication that once the last sub-eventhas been executed, event orchestration of another event is to betriggered, thus resulting in a recursive orchestration of events. Onceevent orchestration computing platform 110 has updated the second eventmaster dataset at step 235, event orchestration computing platform 110may determine that the second sub-event is the last sub-event in thesequence of sub-events for the second event protocol. Accordingly, eventorchestration computing platform 110 may update one or more masterrecords associated with the second event and stored in event recordingcomputing platform 130 to indicate that orchestration of the secondevent has been completed. Event orchestration computing platform 110 mayupdate the one or more master records associated with the second eventand stored in event recording computing platform 130 to further indicatethe completion date and/or time of orchestration of the second event.Event orchestration computing platform 110 may update the one or moremaster records associated with the second event and stored in eventrecording computing platform 130 to include the contents or storagelocation of the second event master dataset.

FIG. 5 depicts an illustrative method for multicomputer processing of anevent request from an event origination device with centralized eventorchestration in accordance with one or more example embodiments.Referring to FIG. 5, at step 500, a computing platform having at leastone processor, a memory, and a communication interface may receive, viathe communication interface, a first event request to orchestrate afirst event. At step 505, the computing platform may determine a firstsub-event associated with the first event. At step 510, the computingplatform may receive a first event customized dataset for the firstsub-event. At step 515, the computing platform may generate one or moreorchestration commands for the first sub-event. At step 520, thecomputing platform may send the one or more orchestration commands andthe first event customized dataset to a first sub-event processingdevice. At step 525, the computing platform may receive a first resultsdataset from the first sub-event processing device. At step 530, thecomputing platform may update a master event dataset associated with thefirst event based on the first results dataset. At step 535, thecomputing platform may determine a second sub-event associated with thefirst event. At step 540, the computing platform may receive a secondevent customized dataset for the second sub-event. At step 545, thecomputing platform may generate one or more orchestration commands forthe second sub-event. At step 550, the computing platform may send thesecond event customized dataset and the one or more orchestrationcommands to a second sub-event processing device. At step 555, thecomputing platform may receive a second results dataset from the secondsub-event processing device. At step 560, the computing platform mayupdate the master event dataset associated with the first event based onthe second results dataset.

One or more aspects of the disclosure may be embodied in computer-usabledata or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices to performthe operations described herein. Generally, program modules includeroutines, programs, objects, components, data structures, and the likethat perform particular tasks or implement particular abstract datatypes when executed by one or more processors in a computer or otherdata processing device. The computer-executable instructions may bestored as computer-readable instructions on a computer-readable mediumsuch as a hard disk, optical disk, removable storage media, solid-statememory, RAM, and the like. The functionality of the program modules maybe combined or distributed as desired in various embodiments. Inaddition, the functionality may be embodied in whole or in part infirmware or hardware equivalents, such as integrated circuits,application-specific integrated circuits (ASICs), field programmablegate arrays (FPGA), and the like. Particular data structures may be usedto more effectively implement one or more aspects of the disclosure, andsuch data structures are contemplated to be within the scope of computerexecutable instructions and computer-usable data described herein.

Various aspects described herein may be embodied as a method, anapparatus, or as one or more computer-readable media storingcomputer-executable instructions. Accordingly, those aspects may takethe form of an entirely hardware embodiment, an entirely softwareembodiment, an entirely firmware embodiment, or an embodiment combiningsoftware, hardware, and firmware aspects in any combination. Inaddition, various signals representing data or events as describedherein may be transferred between a source and a destination in the formof light or electromagnetic waves traveling through signal-conductingmedia such as metal wires, optical fibers, or wireless transmissionmedia (e.g., air or space). In general, the one or morecomputer-readable media may be and/or include one or more non-transitorycomputer-readable media.

As described herein, the various methods and acts may be operativeacross one or more computing servers and one or more networks. Thefunctionality may be distributed in any manner, or may be located in asingle computing device (e.g., a server, a client computer, and thelike). For example, in alternative embodiments, one or more of thecomputing platforms discussed above may be combined into a singlecomputing platform, and the various functions of each computing platformmay be performed by the single computing platform. In such arrangements,any and/or all of the above-discussed communications between computingplatforms may correspond to data being accessed, moved, modified,updated, and/or otherwise used by the single computing platform.Additionally or alternatively, one or more of the computing platformsdiscussed above may be implemented in one or more virtual machines thatare provided by one or more physical computing devices. In sucharrangements, the various functions of each computing platform may beperformed by the one or more virtual machines, and any and/or all of theabove-discussed communications between computing platforms maycorrespond to data being accessed, moved, modified, updated, and/orotherwise used by the one or more virtual machines.

Aspects of the disclosure have been described in terms of illustrativeembodiments thereof. Numerous other embodiments, modifications, andvariations within the scope and spirit of the appended claims will occurto persons of ordinary skill in the art from a review of thisdisclosure. For example, one or more of the steps depicted in theillustrative figures may be performed in other than the recited order,and one or more depicted steps may be optional in accordance withaspects of the disclosure.

What is claimed is:
 1. A computing platform, comprising: at least oneprocessor; a communication interface communicatively coupled to the atleast one processor; and memory storing computer-readable instructionsthat, when executed by the at least one processor, cause the computingplatform to: receive, via the communication interface, from a firstevent origination device, a first event request for a first event;determine a first sub-event associated with the first event; receive,via the communication interface, from an event dataset customizationengine, a first event customized dataset generated for the firstsub-event; generate, based on the first sub-event associated with thefirst event received from the first event origination device, one ormore first event orchestration commands directing a first sub-eventprocessing device to execute the first sub-event; send, via thecommunication interface, to the first sub-event processing device, thefirst event customized dataset and the one or more first eventorchestration commands directing the first sub-event processing deviceto execute the first sub-event; receive, via the communicationinterface, from the first sub-event processing device, a first resultsdataset; and update, based on the first results dataset, a first masterevent dataset associated with the first event.
 2. The computing platformof claim 1, wherein determining the first sub-event comprises:determining a first event type of the first event; accessing, in anevent protocol database, a first event protocol of the first event type;and determining the first sub-event based on contents of the first eventprotocol.
 3. The computing platform of claim 2, wherein the memorystores additional computer-readable instructions that, when executed bythe at least one processor, cause the computing platform to: prior todetermining the first sub-event associated with the first event, sendinga command to the event dataset customization engine to generate thefirst master event dataset within the event dataset customizationengine.
 4. The computing platform of claim 3, wherein the first eventcustomized dataset is generated based in part on the first master eventdataset.
 5. The computing platform of claim 2, wherein the memory storesadditional computer-readable instructions that, when executed by the atleast one processor, cause the computing platform to: validate contentsof the first event request with input data requirements specified by thefirst event protocol.
 6. The computing platform of claim 2, wherein thememory stores additional computer-readable instructions that, whenexecuted by the at least one processor, cause the computing platform to:validate contents of the first results dataset with output datarequirements specified for the first sub-event within the first eventprotocol.
 7. The computing platform of claim 2, wherein the memorystores additional computer-readable instructions that, when executed bythe at least one processor, cause the computing platform to: determine asecond sub-event associated with the first event; receive, via thecommunication interface and from the event dataset customization engine,a second event customized dataset generated for the second sub-event;generate, based on the second sub-event associated with the first eventreceived from the first event origination device, one or more secondevent orchestration commands directing a second sub-event processingdevice to execute the second sub-event; send, via the communicationinterface and via an external event processing interface, to the secondsub-event processing device, the second event customized dataset and theone or more second event orchestration commands directing the secondsub-event processing device to execute the second sub-event; receive,via the communication interface and via the external event processinginterface, from the second sub-event processing device, a second resultsdataset; and update, based on the second results dataset, the firstmaster event dataset associated with the first event.
 8. The computingplatform of claim 7, wherein determining the second sub-event associatedwith the first event comprises: accessing, in the event protocoldatabase, the first event protocol of the first event type; anddetermining the second sub-event based on contents of the first eventprotocol.
 9. The computing platform of claim 7, wherein the memorystores additional computer-readable instructions that, when executed bythe at least one processor, cause the computing platform to: validatecontents of the second results dataset with output data requirementsspecified for the second sub-event within the first event protocol. 10.The computing platform of claim 1, wherein the memory stores additionalcomputer-readable instructions that, when executed by the at least oneprocessor, cause the computing platform to: update one or more recordsto indicate that the first event has been completed.
 11. The computingplatform of claim 1, wherein the memory stores additionalcomputer-readable instructions that, when executed by the at least oneprocessor, cause the computing platform to: receive, via thecommunication interface, from a second event origination device, asecond event request for a second event; determine a second sub-eventassociated with the second event; receive, via the communicationinterface and from the event dataset customization engine, a secondevent customized dataset generated for the second sub-event associatedwith the second event; generate, based on the second sub-eventassociated with the second event received from the second eventorigination device, one or more second event orchestration commandsdirecting a second sub-event processing device to execute the secondsub-event; send, via the communication interface, to the secondsub-event processing device, the second event customized dataset and theone or more second event orchestration commands directing the secondsub-event processing device to execute the second sub-event; receive,via the communication interface, from the second sub-event processingdevice, a second results dataset; and update, based on the secondresults dataset, a second master event dataset associated with thesecond event.
 12. The computing platform of claim 11, whereindetermining the second sub-event comprises: determining a second eventtype of the second event; accessing, in an event protocol database, asecond event protocol of the second event type; and determining thesecond sub-event based on contents of the second event protocol.
 13. Thecomputing platform of claim 12, wherein the memory stores additionalcomputer-readable instructions that, when executed by the at least oneprocessor, cause the computing platform to: prior to determining thesecond sub-event associated with the second event, sending a command tothe event dataset customization engine to generate the second masterevent dataset within the event dataset customization engine.
 14. Thecomputing platform of claim 13, wherein the second event customizeddataset is generated based in part on the second master event dataset.15. The computing platform of claim 12, wherein the memory storesadditional computer-readable instructions that, when executed by the atleast one processor, cause the computing platform to: validate contentsof the second event request with input data requirements specified bythe second event protocol.
 16. The computing platform of claim 12,wherein the memory stores additional computer-readable instructionsthat, when executed by the at least one processor, cause the computingplatform to: validate contents of the second results dataset with outputdata requirements specified for the second sub-event within the secondevent protocol.
 17. The computing platform of claim 12, wherein thememory stores additional computer-readable instructions that, whenexecuted by the at least one processor, cause the computing platform to:determine a third sub-event associated with the second event; receive,via the communication interface and from the event dataset customizationengine, a third event customized dataset generated for the thirdsub-event; generate, based on the third sub-event associated with thesecond event received from the second event origination device, one ormore third event orchestration commands directing a third sub-eventprocessing device to execute the third sub-event; send, via thecommunication interface and via an external event processing interface,to the third sub-event processing device, the third event customizeddataset and the one or more third event orchestration commands directingthe third sub-event processing device to execute the third sub-event;receive, via the communication interface and via the external eventprocessing interface, from the third sub-event processing device, athird results dataset; and update, based on the third results dataset,the second master event dataset associated with the second event. 18.The computing platform of claim 17, wherein determining the thirdsub-event associated with the second event comprises: accessing, in theevent protocol database, the second event protocol of the second eventtype; and determining the third sub-event based on contents of thesecond event protocol.
 19. A method, comprising: at a computing platformcomprising at least one processor, memory, and a communicationinterface: receiving, by the at least one processor, via thecommunication interface, from a first event origination device, a firstevent request for a first event; determining, by the at least oneprocessor, a first sub-event associated with the first event; receiving,by the at least one processor, via the communication interface and froman event dataset customization engine, a first event customized datasetgenerated for the first sub-event; generating, by the at least oneprocessor, based on the first sub-event associated with the first eventreceived from the first event origination device, one or more firstevent orchestration commands directing a first sub-event processingdevice to execute the first sub-event; sending, by the at least oneprocessor, via the communication interface, to the first sub-eventprocessing device, the first event customized dataset and the one ormore first event orchestration commands directing the first sub-eventprocessing device to execute the first sub-event; receiving, by the atleast one processor, via the communication interface, from the firstsub-event processing device, a first results dataset; and updating, bythe at least one processor, based on the first results dataset, a firstmaster event dataset associated with the first event.
 20. One or morenon-transitory computer-readable media storing instructions that, whenexecuted by a computing platform comprising at least one processor,memory, and a communication interface, cause the computing platform to:receive, via the communication interface, from a first event originationdevice, a first event request for a first event; determine a firstsub-event associated with the first event; receive, via thecommunication interface and from an event dataset customization engine,a first event customized dataset generated for the first sub-event;generate, based on the first sub-event associated with the first eventreceived from the first event origination device, one or more firstevent orchestration commands directing a first sub-event processingdevice to execute the first sub-event; send, via the communicationinterface, to the first sub-event processing device, the first eventcustomized dataset and the one or more first event orchestrationcommands directing the first sub-event processing device to execute thefirst sub-event; receive, via the communication interface, from thefirst sub-event processing device, a first results dataset; and update,based on the first results dataset, a first master event datasetassociated with the first event.